Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e054c35989c02b9cecc92d090d34210dc6231027b11bcc4e6c65f3ebfb87f478

Tx prefix hash: e884b3058dae9eb998487195434a81d60d3346168a380f947ff7ac94e5346f8c
Tx public key: f874f7f4c38b1218cbf24bda6a48b0b19ae15706da968b7db017c33cf6c05634
Timestamp: 1728306411 Timestamp [UCT]: 2024-10-07 13:06:51 Age [y:d:h:m:s]: 01:044:09:09:59
Block: 1126424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290104 RingCT/type: yes/0
Extra: 01f874f7f4c38b1218cbf24bda6a48b0b19ae15706da968b7db017c33cf6c05634021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 565d58aa2fc5f1034410fe8292b8f7e9002a1449a1ba30b1fb12296d90c19b3e 0.600000000000 1609215 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": 1126434, "vin": [ { "gen": { "height": 1126424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "565d58aa2fc5f1034410fe8292b8f7e9002a1449a1ba30b1fb12296d90c19b3e" } } ], "extra": [ 1, 248, 116, 247, 244, 195, 139, 18, 24, 203, 242, 75, 218, 106, 72, 176, 177, 154, 225, 87, 6, 218, 150, 139, 125, 176, 23, 195, 60, 246, 192, 86, 52, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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