Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d54a3aac89fc7766c9aa35b0dc0ee91bf1ebdc4825cbadbef031cc581783ab11

Tx prefix hash: a95ff0e0ff0c41f7be843de5e1cf77dbf808eea6234f6138c7cb2668a255f0cc
Tx public key: 367dbea1c0a68c5ea896b64650b7a12766954427615fa2577190b1d2d320ea60
Timestamp: 1715971540 Timestamp [UCT]: 2024-05-17 18:45:40 Age [y:d:h:m:s]: 00:335:10:23:34
Block: 1024160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239759 RingCT/type: yes/0
Extra: 01367dbea1c0a68c5ea896b64650b7a12766954427615fa2577190b1d2d320ea6002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1872ff61394cff23fe9c7acb0b326d1911822731adc724b62a31ec5cdf13c9c8 0.600000000000 1489687 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": 1024170, "vin": [ { "gen": { "height": 1024160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1872ff61394cff23fe9c7acb0b326d1911822731adc724b62a31ec5cdf13c9c8" } } ], "extra": [ 1, 54, 125, 190, 161, 192, 166, 140, 94, 168, 150, 182, 70, 80, 183, 161, 39, 102, 149, 68, 39, 97, 95, 162, 87, 113, 144, 177, 210, 211, 32, 234, 96, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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