Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbd497c621b706ded824f49edeaf633624aa4e35de8c2c9940eae233f234834c

Tx prefix hash: 3b505a9f81555b05cc3263ae931f1ef4c4fcd0c4eff2420379f3e7e2d9e63963
Tx public key: 8a011c0dbf2ee47ee642f07e226c7c02b9ec6c14dc265612c60f88202dbfe645
Timestamp: 1734430532 Timestamp [UCT]: 2024-12-17 10:15:32 Age [y:d:h:m:s]: 00:182:09:16:46
Block: 1177105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130045 RingCT/type: yes/0
Extra: 018a011c0dbf2ee47ee642f07e226c7c02b9ec6c14dc265612c60f88202dbfe645021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50494bfecb3f6bfca4fd9a437037c2baa57c898f3ac74c205a28eac8f70f0a85 0.600000000000 1663468 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": 1177115, "vin": [ { "gen": { "height": 1177105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50494bfecb3f6bfca4fd9a437037c2baa57c898f3ac74c205a28eac8f70f0a85" } } ], "extra": [ 1, 138, 1, 28, 13, 191, 46, 228, 126, 230, 66, 240, 126, 34, 108, 124, 2, 185, 236, 108, 20, 220, 38, 86, 18, 198, 15, 136, 32, 45, 191, 230, 69, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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