Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d1cb45d7310d0d07e9ccefeb53bc2acab59858a26407aa4a6e0680c5966152d

Tx prefix hash: b572b1c2e778cbbb70e5d4f555355b9293bafcb2b063a98231681d050d27445a
Tx public key: a09e16bac85a64abfa07ec078b3e5d30e6119940e52defe4fd5f8764ebf7a2ca
Timestamp: 1736467806 Timestamp [UCT]: 2025-01-10 00:10:06 Age [y:d:h:m:s]: 00:295:22:43:57
Block: 1193947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209001 RingCT/type: yes/0
Extra: 01a09e16bac85a64abfa07ec078b3e5d30e6119940e52defe4fd5f8764ebf7a2ca021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2fa34d9838cac0fbca273bc4c9f9baeef253189faf885b4a09497229df724d0 0.600000000000 1680512 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": 1193957, "vin": [ { "gen": { "height": 1193947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2fa34d9838cac0fbca273bc4c9f9baeef253189faf885b4a09497229df724d0" } } ], "extra": [ 1, 160, 158, 22, 186, 200, 90, 100, 171, 250, 7, 236, 7, 139, 62, 93, 48, 230, 17, 153, 64, 229, 45, 239, 228, 253, 95, 135, 100, 235, 247, 162, 202, 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