Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf19f36699d3e46ff869dfbb77ff22657d4214dbf8c21f4bc9fa3a9b41554b3c

Tx prefix hash: 801a96f422c025333f8463f2357c514fadb1a6bdf31023caabd17902a292b139
Tx public key: 9161b74f076f26cbf2efe49150a8de902e49cb4cae291bdc754bd8f18f48a126
Timestamp: 1732170856 Timestamp [UCT]: 2024-11-21 06:34:16 Age [y:d:h:m:s]: 00:213:19:22:08
Block: 1158356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152473 RingCT/type: yes/0
Extra: 019161b74f076f26cbf2efe49150a8de902e49cb4cae291bdc754bd8f18f48a126021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44bedb24866a3eb2d75a8f3564cac7bb114cebe8aa688f89f2145aa0ef65e6e7 0.600000000000 1643985 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": 1158366, "vin": [ { "gen": { "height": 1158356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44bedb24866a3eb2d75a8f3564cac7bb114cebe8aa688f89f2145aa0ef65e6e7" } } ], "extra": [ 1, 145, 97, 183, 79, 7, 111, 38, 203, 242, 239, 228, 145, 80, 168, 222, 144, 46, 73, 203, 76, 174, 41, 27, 220, 117, 75, 216, 241, 143, 72, 161, 38, 2, 17, 0, 0, 0, 5, 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