Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbee9cd885b1939a940923fccf5ad1ba4de0bc7d747acf833012a255e8787527

Tx prefix hash: 462684d0797cb2c1d266009c6239a7e54125341a4e0e698f157d62ab38fce61e
Tx public key: 5904a3ab93945731e8e4f6e245d976b77e7e3afe6c7990389486767cc3348b87
Timestamp: 1736586479 Timestamp [UCT]: 2025-01-11 09:07:59 Age [y:d:h:m:s]: 00:158:20:38:47
Block: 1194930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113211 RingCT/type: yes/0
Extra: 015904a3ab93945731e8e4f6e245d976b77e7e3afe6c7990389486767cc3348b87021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b8780c1c6a7e2494319e7ab30bdf7ba8482d9e3e724d05e46d96c70d9a48357 0.600000000000 1681509 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": 1194940, "vin": [ { "gen": { "height": 1194930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b8780c1c6a7e2494319e7ab30bdf7ba8482d9e3e724d05e46d96c70d9a48357" } } ], "extra": [ 1, 89, 4, 163, 171, 147, 148, 87, 49, 232, 228, 246, 226, 69, 217, 118, 183, 126, 126, 58, 254, 108, 121, 144, 56, 148, 134, 118, 124, 195, 52, 139, 135, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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