Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbd07ecff2982f6117453009f1b841e77532746f565d631caa57921e6188cba5

Tx prefix hash: ce3344d3f17a9a4962e59f12311c5501bcca0c815e20c67a522bcccdda708346
Tx public key: 694acf999e2f0b2415d11d3a28c25b0fef09b6c7c796f9593cfca53d1a8eab6c
Timestamp: 1737986402 Timestamp [UCT]: 2025-01-27 14:00:02 Age [y:d:h:m:s]: 00:297:08:27:57
Block: 1206271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210259 RingCT/type: yes/0
Extra: 01694acf999e2f0b2415d11d3a28c25b0fef09b6c7c796f9593cfca53d1a8eab6c021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1376ee619ca6613797b1cd9bdafed68e445fbe29a3870a232bec567d8227d3c5 0.600000000000 1692974 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": 1206281, "vin": [ { "gen": { "height": 1206271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1376ee619ca6613797b1cd9bdafed68e445fbe29a3870a232bec567d8227d3c5" } } ], "extra": [ 1, 105, 74, 207, 153, 158, 47, 11, 36, 21, 209, 29, 58, 40, 194, 91, 15, 239, 9, 182, 199, 199, 150, 249, 89, 60, 252, 165, 61, 26, 142, 171, 108, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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