Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36f17921dc4653ba9d678e60f52d6b881ef6e548ffb14ffba8e7aaffdd5b0a65

Tx prefix hash: ab64437f3ef2eaac61a298f7ba9f790f45c38e52fcd9c0eb3aeff19ac0e9b142
Tx public key: 2ba6a32654a728a8e4f3a2ef16c0bdd25be9d6d713ef0ea3cf8d9f4b32f1ae4d
Timestamp: 1719929614 Timestamp [UCT]: 2024-07-02 14:13:34 Age [y:d:h:m:s]: 00:145:04:47:28
Block: 1056974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103903 RingCT/type: yes/0
Extra: 012ba6a32654a728a8e4f3a2ef16c0bdd25be9d6d713ef0ea3cf8d9f4b32f1ae4d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cc23e98e6c573ad8975829190d888837d92936f235fa754e7ef6a69851b598d 0.600000000000 1527403 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": 1056984, "vin": [ { "gen": { "height": 1056974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cc23e98e6c573ad8975829190d888837d92936f235fa754e7ef6a69851b598d" } } ], "extra": [ 1, 43, 166, 163, 38, 84, 167, 40, 168, 228, 243, 162, 239, 22, 192, 189, 210, 91, 233, 214, 215, 19, 239, 14, 163, 207, 141, 159, 75, 50, 241, 174, 77, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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