Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0210ced74eb068fdc4b3f86089217282a434df3538a043fbbe90a6806cf41d8

Tx prefix hash: cd262b14bd5567d949256db19b505277bc36f70ab1178793c1f433486ce08e66
Tx public key: 0ab5d3e91e92cb6a0c676f6c72bbf4dc0b9d8472c2c748a8959ae7dfac86f923
Timestamp: 1726106692 Timestamp [UCT]: 2024-09-12 02:04:52 Age [y:d:h:m:s]: 00:210:01:39:43
Block: 1108177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149983 RingCT/type: yes/0
Extra: 010ab5d3e91e92cb6a0c676f6c72bbf4dc0b9d8472c2c748a8959ae7dfac86f92302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c37ab83b0bd6ad02415034b750ef16dd272dca80b819c77149eeb984574ced 0.600000000000 1585984 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": 1108187, "vin": [ { "gen": { "height": 1108177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c37ab83b0bd6ad02415034b750ef16dd272dca80b819c77149eeb984574ced" } } ], "extra": [ 1, 10, 181, 211, 233, 30, 146, 203, 106, 12, 103, 111, 108, 114, 187, 244, 220, 11, 157, 132, 114, 194, 199, 72, 168, 149, 154, 231, 223, 172, 134, 249, 35, 2, 17, 0, 0, 0, 4, 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