Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 983e2cb93b115c4142016ad12af6ab0bbb168af65f44111e9d0aa27a434879a0

Tx prefix hash: ff5106d9adcece6779379b1b3e199c9e78b789581bcb1ffa5601ebe153c4c65d
Tx public key: b88b585c056a282ce01c5c8429fcb2ca8d4af0e8be825c8337acc77c51109816
Timestamp: 1703440714 Timestamp [UCT]: 2023-12-24 17:58:34 Age [y:d:h:m:s]: 01:157:09:56:11
Block: 920269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373667 RingCT/type: yes/0
Extra: 01b88b585c056a282ce01c5c8429fcb2ca8d4af0e8be825c8337acc77c5110981602110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6668fdbdb018e9c0913fc7dc5a70b8b53c786692343d5a52ec4bad9c18f3436d 0.600000000000 1377947 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": 920279, "vin": [ { "gen": { "height": 920269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6668fdbdb018e9c0913fc7dc5a70b8b53c786692343d5a52ec4bad9c18f3436d" } } ], "extra": [ 1, 184, 139, 88, 92, 5, 106, 40, 44, 224, 28, 92, 132, 41, 252, 178, 202, 141, 74, 240, 232, 190, 130, 92, 131, 55, 172, 199, 124, 81, 16, 152, 22, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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