Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 082988c7183aec35c05a673d590a614a931fdc5f927dde2d1c81c052043c3f19

Tx prefix hash: 7568147b69f30c07d15776b2a8dbc8a2549fe88a4fd85eb262e6f69984cfaed8
Tx public key: 1f0ecfd1ac17c0e1dfdea1016c90d7630fb9e196255563acbca161118300606a
Timestamp: 1746411783 Timestamp [UCT]: 2025-05-05 02:23:03 Age [y:d:h:m:s]: 00:199:05:38:26
Block: 1275988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140119 RingCT/type: yes/0
Extra: 011f0ecfd1ac17c0e1dfdea1016c90d7630fb9e196255563acbca161118300606a021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a849b1ad6c1a2f6c20731dac9648a080dc4e0ca4e9181cd58fc40f021da597b2 0.600000000000 1763303 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": 1275998, "vin": [ { "gen": { "height": 1275988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a849b1ad6c1a2f6c20731dac9648a080dc4e0ca4e9181cd58fc40f021da597b2" } } ], "extra": [ 1, 31, 14, 207, 209, 172, 23, 192, 225, 223, 222, 161, 1, 108, 144, 215, 99, 15, 185, 225, 150, 37, 85, 99, 172, 188, 161, 97, 17, 131, 0, 96, 106, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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