Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f5cf65507a2c65c40ca848ed93b1274b24d8d32012b4a22a88f7f202fd21e9

Tx prefix hash: ebd8e9ad08255fcb6f45d7f8bcfef73e5abc605137d54108b388150740dbebca
Tx public key: 1542b05b7dac5cb4455cb1f0a5676a96a07d0b83176c668d750e39fcad541329
Timestamp: 1707912590 Timestamp [UCT]: 2024-02-14 12:09:50 Age [y:d:h:m:s]: 01:054:22:25:15
Block: 957334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300312 RingCT/type: yes/0
Extra: 011542b05b7dac5cb4455cb1f0a5676a96a07d0b83176c668d750e39fcad54132902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17966944c474d4e1f60a4ff3f7a947863871d4f4402c1358d93576f2c63b4f23 0.600000000000 1416652 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": 957344, "vin": [ { "gen": { "height": 957334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17966944c474d4e1f60a4ff3f7a947863871d4f4402c1358d93576f2c63b4f23" } } ], "extra": [ 1, 21, 66, 176, 91, 125, 172, 92, 180, 69, 92, 177, 240, 165, 103, 106, 150, 160, 125, 11, 131, 23, 108, 102, 141, 117, 14, 57, 252, 173, 84, 19, 41, 2, 17, 0, 0, 0, 3, 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