Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c959f90d78aa4449c948999cecbabce9dd0ce4bc893163e94b3870c9a00ab40f

Tx prefix hash: c62bc7590dfde028436624a8a42dc19c1b121bc85e943e593660a641a8b06c34
Tx public key: 9d2e9767cc30b6d92228e3f940a14f0145fd87b47ee763eedf5c7ee4f520356c
Timestamp: 1726541063 Timestamp [UCT]: 2024-09-17 02:44:23 Age [y:d:h:m:s]: 00:055:03:22:18
Block: 1111780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39409 RingCT/type: yes/0
Extra: 019d2e9767cc30b6d92228e3f940a14f0145fd87b47ee763eedf5c7ee4f520356c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4bce3f7e7431eff7931286c052313d593ed03ac7197ade84d7f5838ced0db2a 0.600000000000 1590861 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": 1111790, "vin": [ { "gen": { "height": 1111780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4bce3f7e7431eff7931286c052313d593ed03ac7197ade84d7f5838ced0db2a" } } ], "extra": [ 1, 157, 46, 151, 103, 204, 48, 182, 217, 34, 40, 227, 249, 64, 161, 79, 1, 69, 253, 135, 180, 126, 231, 99, 238, 223, 92, 126, 228, 245, 32, 53, 108, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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