Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36edaf2c72713f669d7be0139db79898b50e6e97c7106b897a75384b27689f78

Tx prefix hash: 8333c71e042f708d590a596480c39f1b42e12b2db796e0e499d4c15429268f7e
Tx public key: 273b0c86f7aa1b5cc1b4034d55049985c9b4554d496af6c782b4750ef05af718
Timestamp: 1729365521 Timestamp [UCT]: 2024-10-19 19:18:41 Age [y:d:h:m:s]: 00:171:00:50:19
Block: 1135199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122007 RingCT/type: yes/0
Extra: 01273b0c86f7aa1b5cc1b4034d55049985c9b4554d496af6c782b4750ef05af718021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f45ff951a694572f222dd0cae2273adc2d11391c71dcfb08cfeb1d3f83ea86cf 0.600000000000 1618530 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": 1135209, "vin": [ { "gen": { "height": 1135199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f45ff951a694572f222dd0cae2273adc2d11391c71dcfb08cfeb1d3f83ea86cf" } } ], "extra": [ 1, 39, 59, 12, 134, 247, 170, 27, 92, 193, 180, 3, 77, 85, 4, 153, 133, 201, 180, 85, 77, 73, 106, 246, 199, 130, 180, 117, 14, 240, 90, 247, 24, 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