Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd54a30df0195fc8980f4867b514e33472b9c62681ebc25ad03d44d014629dc7

Tx prefix hash: 38f76ddab188c5a0a2452f7d6a75cc411b63eed5bba11bc0843ecaeec0db9a41
Tx public key: 82376344471823a2646431eac41a86d1dd5cce6ba014705b58073d8ff2114b82
Timestamp: 1676579294 Timestamp [UCT]: 2023-02-16 20:28:14 Age [y:d:h:m:s]: 02:102:10:44:52
Block: 698465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594867 RingCT/type: yes/0
Extra: 0182376344471823a2646431eac41a86d1dd5cce6ba014705b58073d8ff2114b8202110000000474b6d784000000000000000000

1 output(s) for total of 2.976428291000 dcy

stealth address amount amount idx
00: 5a42b01ff6b0f9a9a237e6663f3a0b37aa2bc20a11a792a3c05bb2e77c92b88f 2.976428291000 1141768 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": 698475, "vin": [ { "gen": { "height": 698465 } } ], "vout": [ { "amount": 2976428291, "target": { "key": "5a42b01ff6b0f9a9a237e6663f3a0b37aa2bc20a11a792a3c05bb2e77c92b88f" } } ], "extra": [ 1, 130, 55, 99, 68, 71, 24, 35, 162, 100, 100, 49, 234, 196, 26, 134, 209, 221, 92, 206, 107, 160, 20, 112, 91, 88, 7, 61, 143, 242, 17, 75, 130, 2, 17, 0, 0, 0, 4, 116, 182, 215, 132, 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