Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 433b1d01b39118b898b019e2ab768b96ebcc10c2c6fb8c10a77f155c3b3753f2

Tx prefix hash: 251f04cf9e95bf77358119eeb8be3de3e1a963a8ef84475712e986ba5523e4d8
Tx public key: d9c0ff51967a9503fea6b575a680309fcf02774a5a9d0e8a469b44c9484761c2
Timestamp: 1734961012 Timestamp [UCT]: 2024-12-23 13:36:52 Age [y:d:h:m:s]: 00:103:22:15:44
Block: 1181500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74035 RingCT/type: yes/0
Extra: 01d9c0ff51967a9503fea6b575a680309fcf02774a5a9d0e8a469b44c9484761c20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d90020902bd0412134f6a1267297ce73bb1a991d57fef647e58a247104a272a 0.600000000000 1667925 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": 1181510, "vin": [ { "gen": { "height": 1181500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d90020902bd0412134f6a1267297ce73bb1a991d57fef647e58a247104a272a" } } ], "extra": [ 1, 217, 192, 255, 81, 150, 122, 149, 3, 254, 166, 181, 117, 166, 128, 48, 159, 207, 2, 119, 74, 90, 157, 14, 138, 70, 155, 68, 201, 72, 71, 97, 194, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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