Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24cb8808d3a72da805d94c0bb04ec0fe7ceff95f674750a7559338534b748c98

Tx prefix hash: dc1b2220cc333cc31cb91d750616907256a68631c8619b8f325b035a305cf736
Tx public key: c0b5a81b7cfeaeb2499fc8dac76f3d656282e223a1ab9f18f82cec501dea1a44
Timestamp: 1735954960 Timestamp [UCT]: 2025-01-04 01:42:40 Age [y:d:h:m:s]: 00:277:06:09:07
Block: 1189700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195606 RingCT/type: yes/0
Extra: 01c0b5a81b7cfeaeb2499fc8dac76f3d656282e223a1ab9f18f82cec501dea1a44021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e427a35272f9aee3bf6322ef30dd58b85ccee69cc23d4a7f8d7384c969da052 0.600000000000 1676211 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": 1189710, "vin": [ { "gen": { "height": 1189700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e427a35272f9aee3bf6322ef30dd58b85ccee69cc23d4a7f8d7384c969da052" } } ], "extra": [ 1, 192, 181, 168, 27, 124, 254, 174, 178, 73, 159, 200, 218, 199, 111, 61, 101, 98, 130, 226, 35, 161, 171, 159, 24, 248, 44, 236, 80, 29, 234, 26, 68, 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