Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72308179cbde2ee7414f6ee75836e09da5050af939aa8aa87507152c44aea27

Tx prefix hash: 976e22ad9c42298e5a3f4f8b22c633ce0dfa776aa080c778d3d6c8ac1904aa00
Tx public key: 2a54a3c3aba3df3c7384aeef430f748b73054cab7aec18cfdd44aef7b8634eac
Timestamp: 1724394594 Timestamp [UCT]: 2024-08-23 06:29:54 Age [y:d:h:m:s]: 00:183:22:04:55
Block: 1094007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131252 RingCT/type: yes/0
Extra: 012a54a3c3aba3df3c7384aeef430f748b73054cab7aec18cfdd44aef7b8634eac021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26a2c13cb5aa6013c09ae0f93ba88d144adebf6becb2b47fd4f2fd0262318dc9 0.600000000000 1569064 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": 1094017, "vin": [ { "gen": { "height": 1094007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26a2c13cb5aa6013c09ae0f93ba88d144adebf6becb2b47fd4f2fd0262318dc9" } } ], "extra": [ 1, 42, 84, 163, 195, 171, 163, 223, 60, 115, 132, 174, 239, 67, 15, 116, 139, 115, 5, 76, 171, 122, 236, 24, 207, 221, 68, 174, 247, 184, 99, 78, 172, 2, 17, 0, 0, 0, 2, 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