Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c536e03f4501dd537c2adc65b222fbd6d74eb5694509c385e9b76c494c5e2867

Tx prefix hash: 9801c5f78db5b2195d473239c80014d697e4e9ac756b14abd66d69287db3e467
Tx public key: 1d54c487824f9cfbcec7db6215f7e2c04ca11e70c3d80fa896ea64c8069210b6
Timestamp: 1723285485 Timestamp [UCT]: 2024-08-10 10:24:45 Age [y:d:h:m:s]: 01:093:03:14:53
Block: 1084803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325028 RingCT/type: yes/0
Extra: 011d54c487824f9cfbcec7db6215f7e2c04ca11e70c3d80fa896ea64c8069210b6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3204b8fd7d39e18d7bc301eeaefc0d8a8d9845d89f0fd6554dd5bd4369cfeba4 0.600000000000 1559206 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": 1084813, "vin": [ { "gen": { "height": 1084803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3204b8fd7d39e18d7bc301eeaefc0d8a8d9845d89f0fd6554dd5bd4369cfeba4" } } ], "extra": [ 1, 29, 84, 196, 135, 130, 79, 156, 251, 206, 199, 219, 98, 21, 247, 226, 192, 76, 161, 30, 112, 195, 216, 15, 168, 150, 234, 100, 200, 6, 146, 16, 182, 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