Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6483d98eee04f629b84b2e8ed2cc884f1321e1fec206e3131261057a71be14a1

Tx prefix hash: 9ed332c5661d140060bbddaa786d51c97daf9bbbd2e10e94ad2290f8301ba853
Tx public key: 8ac97daa41d522ce9d9b53e544e2f4c55b7c071f683ce102267491ba26b40e0b
Timestamp: 1726757529 Timestamp [UCT]: 2024-09-19 14:52:09 Age [y:d:h:m:s]: 00:112:13:41:06
Block: 1113579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80488 RingCT/type: yes/0
Extra: 018ac97daa41d522ce9d9b53e544e2f4c55b7c071f683ce102267491ba26b40e0b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c29bf60aab4acf8b2d9d283a7272e3aa3536c2d1b8981814ce51e4a6270841c5 0.600000000000 1593302 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": 1113589, "vin": [ { "gen": { "height": 1113579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c29bf60aab4acf8b2d9d283a7272e3aa3536c2d1b8981814ce51e4a6270841c5" } } ], "extra": [ 1, 138, 201, 125, 170, 65, 213, 34, 206, 157, 155, 83, 229, 68, 226, 244, 197, 91, 124, 7, 31, 104, 60, 225, 2, 38, 116, 145, 186, 38, 180, 14, 11, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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