Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64968f9c3bb09e498a78e17b0abbef3bd2cf68d11c54f0be0a24e259dd4cd7a0

Tx prefix hash: 004fe53b85cda2ed179bb0b085e8bc4dfedc0ab1f12b93859c0aae095ef32806
Tx public key: 9da7bf66af92f18920ebcebd5c9e3cd86013c1e4e474807ba0d83270cf74a17c
Timestamp: 1702561210 Timestamp [UCT]: 2023-12-14 13:40:10 Age [y:d:h:m:s]: 01:357:17:09:20
Block: 912976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514547 RingCT/type: yes/0
Extra: 019da7bf66af92f18920ebcebd5c9e3cd86013c1e4e474807ba0d83270cf74a17c021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a06a6470a3da4d0353987217d56ac058a357402ab4117d3166afefba242e203a 0.600000000000 1370214 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": 912986, "vin": [ { "gen": { "height": 912976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a06a6470a3da4d0353987217d56ac058a357402ab4117d3166afefba242e203a" } } ], "extra": [ 1, 157, 167, 191, 102, 175, 146, 241, 137, 32, 235, 206, 189, 92, 158, 60, 216, 96, 19, 193, 228, 228, 116, 128, 123, 160, 216, 50, 112, 207, 116, 161, 124, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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