Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 272e12ae901b62c4ebe68beb5d64ce51441838ea99ea7e16dd78121aaba694a0

Tx prefix hash: 49853205d35faf4ae0a38f8a20f0522d4f40e3fdf25ce6a2559c4bf77eec67b2
Tx public key: 34b551487d96d87f0b7e178483dc707dce47fc3e78ede1e9d3eb8ed30e9826e0
Timestamp: 1737156624 Timestamp [UCT]: 2025-01-17 23:30:24 Age [y:d:h:m:s]: 00:337:12:11:47
Block: 1199641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238767 RingCT/type: yes/0
Extra: 0134b551487d96d87f0b7e178483dc707dce47fc3e78ede1e9d3eb8ed30e9826e0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f6f49df2cc32bf5887f1d2cf9416c0bff95b93116fb4084973abe22d4fc848c 0.600000000000 1686274 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": 1199651, "vin": [ { "gen": { "height": 1199641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f6f49df2cc32bf5887f1d2cf9416c0bff95b93116fb4084973abe22d4fc848c" } } ], "extra": [ 1, 52, 181, 81, 72, 125, 150, 216, 127, 11, 126, 23, 132, 131, 220, 112, 125, 206, 71, 252, 62, 120, 237, 225, 233, 211, 235, 142, 211, 14, 152, 38, 224, 2, 17, 0, 0, 0, 2, 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