Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250ca135939eb4162cddb52631040b1f6bcc31cd18c2a66579d5efb87b8a7647

Tx prefix hash: cc0f11300aca78b1467098a3cf7a3367d755dc5925eb16179014b4ec57d8d92a
Tx public key: 02309330ce21aa727b29eabb13e74dd7b73dba5b0acc53eb3e780b586cc9df5c
Timestamp: 1702951342 Timestamp [UCT]: 2023-12-19 02:02:22 Age [y:d:h:m:s]: 01:129:20:03:19
Block: 916219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353932 RingCT/type: yes/0
Extra: 0102309330ce21aa727b29eabb13e74dd7b73dba5b0acc53eb3e780b586cc9df5c02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a620fb35c07356c647cd692e1d7d9d5c086a9bed364b425875d4d4cf82728d5 0.600000000000 1373701 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": 916229, "vin": [ { "gen": { "height": 916219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a620fb35c07356c647cd692e1d7d9d5c086a9bed364b425875d4d4cf82728d5" } } ], "extra": [ 1, 2, 48, 147, 48, 206, 33, 170, 114, 123, 41, 234, 187, 19, 231, 77, 215, 183, 61, 186, 91, 10, 204, 83, 235, 62, 120, 11, 88, 108, 201, 223, 92, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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