Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7a4837f81eccdead86678f56d0d4cf72a2707df9291aa48168f07d4add80e82

Tx prefix hash: ded240397ad5c8299255a063770fa421736674443c595f8e68deef60fb6e9767
Tx public key: e87936c68575072d4e1f9dd00f1bb10e71d4d43d233aa2fabdd6f0c3effa570e
Timestamp: 1726800855 Timestamp [UCT]: 2024-09-20 02:54:15 Age [y:d:h:m:s]: 00:245:16:22:33
Block: 1113933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175448 RingCT/type: yes/0
Extra: 01e87936c68575072d4e1f9dd00f1bb10e71d4d43d233aa2fabdd6f0c3effa570e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c93c89bb073448db2d961db9811f40d8e50297f5979e17bd1d7013f17126e8c2 0.600000000000 1593730 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": 1113943, "vin": [ { "gen": { "height": 1113933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c93c89bb073448db2d961db9811f40d8e50297f5979e17bd1d7013f17126e8c2" } } ], "extra": [ 1, 232, 121, 54, 198, 133, 117, 7, 45, 78, 31, 157, 208, 15, 27, 177, 14, 113, 212, 212, 61, 35, 58, 162, 250, 189, 214, 240, 195, 239, 250, 87, 14, 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