Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c7c6142fe61a942b1431e461c4fded5e676c99db62be2d0d3da8e2c7c234d38

Tx prefix hash: a454010a75971df411d22023e76f30b3a4c1a4c7f28867da8374a9826ed51cea
Tx public key: aa5a23cd014757b040015309d366a78887eaa437132f42364a4a834c2423edf1
Timestamp: 1726183198 Timestamp [UCT]: 2024-09-12 23:19:58 Age [y:d:h:m:s]: 00:257:21:44:55
Block: 1108815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184202 RingCT/type: yes/0
Extra: 01aa5a23cd014757b040015309d366a78887eaa437132f42364a4a834c2423edf1021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afe82da30a5d4a871cf793fd567ef9bbf2c62ba9cf5ea5c6870e8bda1c54e402 0.600000000000 1586848 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": 1108825, "vin": [ { "gen": { "height": 1108815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afe82da30a5d4a871cf793fd567ef9bbf2c62ba9cf5ea5c6870e8bda1c54e402" } } ], "extra": [ 1, 170, 90, 35, 205, 1, 71, 87, 176, 64, 1, 83, 9, 211, 102, 167, 136, 135, 234, 164, 55, 19, 47, 66, 54, 74, 74, 131, 76, 36, 35, 237, 241, 2, 17, 0, 0, 0, 6, 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