Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fa50fc9d85052fa68d8a74a07fd161a799ea26f9f40a345cb0b9ce406221534

Tx prefix hash: 7e5d6369e0b8691657e2a5a33218d197221ca99887908021f7698464d67a3e90
Tx public key: bea2695e367b78e38fed26e57dceaf8e603d98cf02fe515b7a39d60fcdccacc3
Timestamp: 1576279930 Timestamp [UCT]: 2019-12-13 23:32:10 Age [y:d:h:m:s]: 04:341:22:21:55
Block: 26447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130224 RingCT/type: yes/0
Extra: 01bea2695e367b78e38fed26e57dceaf8e603d98cf02fe515b7a39d60fcdccacc3021100000007d81c26c0000000000000000000

1 output(s) for total of 501.615534672000 dcy

stealth address amount amount idx
00: bce3350ca8f6b2ca0784bbad28df89adcc36d5dc9abffa948bb8bbf6bcc3b981 501.615534672000 43872 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": 26457, "vin": [ { "gen": { "height": 26447 } } ], "vout": [ { "amount": 501615534672, "target": { "key": "bce3350ca8f6b2ca0784bbad28df89adcc36d5dc9abffa948bb8bbf6bcc3b981" } } ], "extra": [ 1, 190, 162, 105, 94, 54, 123, 120, 227, 143, 237, 38, 229, 125, 206, 175, 142, 96, 61, 152, 207, 2, 254, 81, 91, 122, 57, 214, 15, 205, 204, 172, 195, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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