Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d62a07cf19b453f74d20ab915050f34e0b8f2c3368203e9cb8ca19580e4b81f6

Tx prefix hash: fc85835e22e6b868419e300daf8b4dd6af1eba0263d83b4672a5744d210cb31d
Tx public key: 36d7891e74b18d09af4680104bc788a34e506b8ed7c930427bd5f03b2c3f0cd4
Timestamp: 1716598856 Timestamp [UCT]: 2024-05-25 01:00:56 Age [y:d:h:m:s]: 00:218:10:26:51
Block: 1029367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156322 RingCT/type: yes/0
Extra: 0136d7891e74b18d09af4680104bc788a34e506b8ed7c930427bd5f03b2c3f0cd40211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90752dda8c05c6c82efef3943e60ff923e4e8befa28a196b1448d0a4bd22ee6b 0.600000000000 1497438 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": 1029377, "vin": [ { "gen": { "height": 1029367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90752dda8c05c6c82efef3943e60ff923e4e8befa28a196b1448d0a4bd22ee6b" } } ], "extra": [ 1, 54, 215, 137, 30, 116, 177, 141, 9, 175, 70, 128, 16, 75, 199, 136, 163, 78, 80, 107, 142, 215, 201, 48, 66, 123, 213, 240, 59, 44, 63, 12, 212, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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