Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495aa9586063df687033cce169f9a03196bf723d08d399dbefdef003c7a5dd08

Tx prefix hash: 0560a0d094ab55f624b734c6888e478de6a6c39a98b3dd89760f79afd4e2204e
Tx public key: 065a4b12ecf791e85038d7b35329c77c124585ae80b811be042bbbe3589c7329
Timestamp: 1728279876 Timestamp [UCT]: 2024-10-07 05:44:36 Age [y:d:h:m:s]: 01:045:09:18:50
Block: 1126199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290821 RingCT/type: yes/0
Extra: 01065a4b12ecf791e85038d7b35329c77c124585ae80b811be042bbbe3589c732902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44cb76da31b1929e7067e60ac2c169927dfdfb892f9e9a790365e22c0fa6c241 0.600000000000 1608988 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": 1126209, "vin": [ { "gen": { "height": 1126199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44cb76da31b1929e7067e60ac2c169927dfdfb892f9e9a790365e22c0fa6c241" } } ], "extra": [ 1, 6, 90, 75, 18, 236, 247, 145, 232, 80, 56, 215, 179, 83, 41, 199, 124, 18, 69, 133, 174, 128, 184, 17, 190, 4, 43, 187, 227, 88, 156, 115, 41, 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