Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f82aa0096d0ed538ef872f4733426b49da6fab31ba870013e3a1a3d59deb931a

Tx prefix hash: c1859ee63fbe38ffa9130f4203bd90dbef5df4df13ca56bec3170fb1dd8ff7aa
Tx public key: 88b5a9efbc05a1d7ab2f027ec804ecb690ef5f812d6a023aa381cac99374f52d
Timestamp: 1709622509 Timestamp [UCT]: 2024-03-05 07:08:29 Age [y:d:h:m:s]: 01:245:22:49:24
Block: 971524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434489 RingCT/type: yes/0
Extra: 0188b5a9efbc05a1d7ab2f027ec804ecb690ef5f812d6a023aa381cac99374f52d02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a297572f62fd64668d583888b0e49385bab95846011d5016fd50466eb1a13ca 0.600000000000 1431421 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": 971534, "vin": [ { "gen": { "height": 971524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a297572f62fd64668d583888b0e49385bab95846011d5016fd50466eb1a13ca" } } ], "extra": [ 1, 136, 181, 169, 239, 188, 5, 161, 215, 171, 47, 2, 126, 200, 4, 236, 182, 144, 239, 95, 129, 45, 106, 2, 58, 163, 129, 202, 201, 147, 116, 245, 45, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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