Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab4474617dfc1ff5579c7c24e22b865defa277c7921fdd92dd9e660bfa6566c9

Tx prefix hash: d0481c667b20d6b1afce14f965b0bdea142b5b2322278e6cfac4c4f046a2bbd1
Tx public key: 3b8c274ce4a34359f2d7cad248fd9d33b65138026ee1532a7070fb8fab3dd47f
Timestamp: 1681680826 Timestamp [UCT]: 2023-04-16 21:33:46 Age [y:d:h:m:s]: 02:029:19:25:33
Block: 740107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543479 RingCT/type: yes/0
Extra: 013b8c274ce4a34359f2d7cad248fd9d33b65138026ee1532a7070fb8fab3dd47f0211000000045029cbac000000000000000000

1 output(s) for total of 2.166299471000 dcy

stealth address amount amount idx
00: 1ea7bd9b579f2a721813292149d682bad545e8123da5d8a74f4237ac224a85c9 2.166299471000 1186988 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": 740117, "vin": [ { "gen": { "height": 740107 } } ], "vout": [ { "amount": 2166299471, "target": { "key": "1ea7bd9b579f2a721813292149d682bad545e8123da5d8a74f4237ac224a85c9" } } ], "extra": [ 1, 59, 140, 39, 76, 228, 163, 67, 89, 242, 215, 202, 210, 72, 253, 157, 51, 182, 81, 56, 2, 110, 225, 83, 42, 112, 112, 251, 143, 171, 61, 212, 127, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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