Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d6bf725accd1091b6e5e5bce0a30996bfb4ef52db9ca81c2ecbf5e6b533682

Tx prefix hash: b39dbd4dbed3caeacef34fa1d8204991b2d9590417304cfd642999d9140dfc88
Tx public key: 5cec52e03735a3be904233e55f60050e9b199ac405bff6d3dba7698c481f2a62
Timestamp: 1721244660 Timestamp [UCT]: 2024-07-17 19:31:00 Age [y:d:h:m:s]: 01:113:01:19:07
Block: 1067885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339296 RingCT/type: yes/0
Extra: 015cec52e03735a3be904233e55f60050e9b199ac405bff6d3dba7698c481f2a6202110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa05df6b6765d431e640ca0de3d8862bdc1b8b8bce8c2177cb7399d2d40724d5 0.600000000000 1538822 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": 1067895, "vin": [ { "gen": { "height": 1067885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa05df6b6765d431e640ca0de3d8862bdc1b8b8bce8c2177cb7399d2d40724d5" } } ], "extra": [ 1, 92, 236, 82, 224, 55, 53, 163, 190, 144, 66, 51, 229, 95, 96, 5, 14, 155, 25, 154, 196, 5, 191, 246, 211, 219, 167, 105, 140, 72, 31, 42, 98, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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