Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b8bde80583a61840a67f4616b6bb73ac21fc9cf39112a10990bf0cd0a685291

Tx prefix hash: 8addb02a426196219d8b2fa81d3c7e10d92fe8b70d87c59e86d7626487c032a1
Tx public key: 7c9b2d3701d8ffff7662e4b59649e58e0baf32802a09445289bfda6f755b3f71
Timestamp: 1735695802 Timestamp [UCT]: 2025-01-01 01:43:22 Age [y:d:h:m:s]: 00:093:00:33:01
Block: 1187546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66264 RingCT/type: yes/0
Extra: 017c9b2d3701d8ffff7662e4b59649e58e0baf32802a09445289bfda6f755b3f71021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ead311d8d7418c0ff38ed3f4849d70e1c12b39c580572bc9988fefc535ae88 0.600000000000 1674037 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": 1187556, "vin": [ { "gen": { "height": 1187546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ead311d8d7418c0ff38ed3f4849d70e1c12b39c580572bc9988fefc535ae88" } } ], "extra": [ 1, 124, 155, 45, 55, 1, 216, 255, 255, 118, 98, 228, 181, 150, 73, 229, 142, 11, 175, 50, 128, 42, 9, 68, 82, 137, 191, 218, 111, 117, 91, 63, 113, 2, 17, 0, 0, 0, 4, 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