Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c71807ecb8d7e5b0ab93ff022c332900ecde86c222671825b7d1e0de2ec9e831

Tx prefix hash: 588c0a1b7779e2daf0a249f9e5bea4593b923c492effa41a4aac3d2c989cd693
Tx public key: 821cbdf750cd32842a814b1015cfc986e5a29e2399d81d342638619c9727b058
Timestamp: 1725269262 Timestamp [UCT]: 2024-09-02 09:27:42 Age [y:d:h:m:s]: 00:073:17:28:43
Block: 1101243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52705 RingCT/type: yes/0
Extra: 01821cbdf750cd32842a814b1015cfc986e5a29e2399d81d342638619c9727b05802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c856b3bb0e6395ebd4a98f559a27e098462d76798c9269680fd69a0b22dca7 0.600000000000 1577228 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": 1101253, "vin": [ { "gen": { "height": 1101243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c856b3bb0e6395ebd4a98f559a27e098462d76798c9269680fd69a0b22dca7" } } ], "extra": [ 1, 130, 28, 189, 247, 80, 205, 50, 132, 42, 129, 75, 16, 21, 207, 201, 134, 229, 162, 158, 35, 153, 216, 29, 52, 38, 56, 97, 156, 151, 39, 176, 88, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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