Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5b55953f4bdf90833481032a9ceb80bffd92152d5583ac4fd82c96b9b3d55f

Tx prefix hash: 54a3fac30085336b728414937e17f8fa17e64002517fbabcfbd4c16940081673
Tx public key: 041f0f91ef2b0d8bb7e8c26d92b6e6d845b6350cdc80f229a19d547209ea10fb
Timestamp: 1738863367 Timestamp [UCT]: 2025-02-06 17:36:07 Age [y:d:h:m:s]: 00:288:05:46:50
Block: 1213514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203759 RingCT/type: yes/0
Extra: 01041f0f91ef2b0d8bb7e8c26d92b6e6d845b6350cdc80f229a19d547209ea10fb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46143b135472ee07481ac348c94bc3c32775cdfccab963d9f8b51a8cb269efe1 0.600000000000 1700293 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": 1213524, "vin": [ { "gen": { "height": 1213514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46143b135472ee07481ac348c94bc3c32775cdfccab963d9f8b51a8cb269efe1" } } ], "extra": [ 1, 4, 31, 15, 145, 239, 43, 13, 139, 183, 232, 194, 109, 146, 182, 230, 216, 69, 182, 53, 12, 220, 128, 242, 41, 161, 157, 84, 114, 9, 234, 16, 251, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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