Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1797de064edaa16b626c2b06e9b6a784465b50a95d00ceddb846aaad66d37f5

Tx prefix hash: 98e110f5d09ffa430ed131c43525745daeeb6a20898bea72aa3853c3e248a024
Tx public key: 791873b4c71c85f4a48c2d39bb3473d7e98e0814beb8d362d18a4a723bfdd987
Timestamp: 1738151231 Timestamp [UCT]: 2025-01-29 11:47:11 Age [y:d:h:m:s]: 00:138:14:21:19
Block: 1207613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99028 RingCT/type: yes/0
Extra: 01791873b4c71c85f4a48c2d39bb3473d7e98e0814beb8d362d18a4a723bfdd9870211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1771b2b2492f5cbd4ad996c3fbbde2036f494db4123ea880a6fc4572f950b76 0.600000000000 1694338 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": 1207623, "vin": [ { "gen": { "height": 1207613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1771b2b2492f5cbd4ad996c3fbbde2036f494db4123ea880a6fc4572f950b76" } } ], "extra": [ 1, 121, 24, 115, 180, 199, 28, 133, 244, 164, 140, 45, 57, 187, 52, 115, 215, 233, 142, 8, 20, 190, 184, 211, 98, 209, 138, 74, 114, 59, 253, 217, 135, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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