Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b26320a1872252d3df38d6e2cb67b09ebbeaf6787130ff1a56e119ed98e375

Tx prefix hash: 9cff1f5039958f299db660ed69a889cb3476780ed1982245a56d087240559435
Tx public key: 41d34a625b2ff1b130a4af7ee81e4f24cff44d42d7d1dfdac6715d84306d14fa
Timestamp: 1720581439 Timestamp [UCT]: 2024-07-10 03:17:19 Age [y:d:h:m:s]: 01:145:03:42:20
Block: 1062378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362294 RingCT/type: yes/0
Extra: 0141d34a625b2ff1b130a4af7ee81e4f24cff44d42d7d1dfdac6715d84306d14fa021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5355170bd1d67f0f8f51297afe2325b5a27400d7882e25a6b4cc5b283e85856 0.600000000000 1532879 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": 1062388, "vin": [ { "gen": { "height": 1062378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5355170bd1d67f0f8f51297afe2325b5a27400d7882e25a6b4cc5b283e85856" } } ], "extra": [ 1, 65, 211, 74, 98, 91, 47, 241, 177, 48, 164, 175, 126, 232, 30, 79, 36, 207, 244, 77, 66, 215, 209, 223, 218, 198, 113, 93, 132, 48, 109, 20, 250, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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