Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161d89f1860c2f29ab17376096c2a024238744a270bdeb9ee88b7a429c5729c1

Tx prefix hash: 8eac336f97e073e845b497109fca8df2629498358e6a3d381f64424777b70c6d
Tx public key: d994b3c32ed723aef22f5d2510eef06f4be64a20de948da39762704ada4ea208
Timestamp: 1700807663 Timestamp [UCT]: 2023-11-24 06:34:23 Age [y:d:h:m:s]: 01:345:18:44:47
Block: 898434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506020 RingCT/type: yes/0
Extra: 01d994b3c32ed723aef22f5d2510eef06f4be64a20de948da39762704ada4ea20802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.647314277000 dcy

stealth address amount amount idx
00: 588240f6a295096b217e37fff2efea72918566115e5ee561f6e596c67eb2069a 0.647314277000 1354849 of 0

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": 898444, "vin": [ { "gen": { "height": 898434 } } ], "vout": [ { "amount": 647314277, "target": { "key": "588240f6a295096b217e37fff2efea72918566115e5ee561f6e596c67eb2069a" } } ], "extra": [ 1, 217, 148, 179, 195, 46, 215, 35, 174, 242, 47, 93, 37, 16, 238, 240, 111, 75, 230, 74, 32, 222, 148, 141, 163, 151, 98, 112, 74, 218, 78, 162, 8, 2, 17, 0, 0, 0, 1, 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