Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ba8390aa24d688d7d58160dc46d64aad2d32fed56e50be91a7b6a298d18f5ef3

Tx prefix hash: 93d2ded5a6c78ef2ebd3a50ee4655372a547d51ea5432262a3acb19b2c909006
Tx public key: db7850d6d9aac5e8e743efbe844575c641b67966cc132b035eb0d10c8e21a87e
Timestamp: 1708243440 Timestamp [UCT]: 2024-02-18 08:04:00 Age [y:d:h:m:s]: 01:039:22:48:24
Block: 960085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289578 RingCT/type: yes/0
Extra: 01db7850d6d9aac5e8e743efbe844575c641b67966cc132b035eb0d10c8e21a87e02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0905f1c27e3932a0a69178486ca0cd39fd0a6bb345d9c02f0b9ebf00de27516f 0.600000000000 1419644 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 960095, "vin": [ { "gen": { "height": 960085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0905f1c27e3932a0a69178486ca0cd39fd0a6bb345d9c02f0b9ebf00de27516f" } } ], "extra": [ 1, 219, 120, 80, 214, 217, 170, 197, 232, 231, 67, 239, 190, 132, 69, 117, 198, 65, 182, 121, 102, 204, 19, 43, 3, 94, 176, 209, 12, 142, 33, 168, 126, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8