Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e8d10459de1054c65b4dd0127fd4f636b591f662cb3cbb83f077dfc8203e372

Tx prefix hash: 67873c67c480b6b50c9dff8da94ca997bce192e83f9c94d5f2f792e2ce7375d7
Tx public key: cbf00c742ea64088d4c5c6323e9eb6065ea3a0970256cd8edb758d37f027b133
Timestamp: 1763014182 Timestamp [UCT]: 2025-11-13 06:09:42 Age [y:d:h:m:s]: 00:051:03:35:06
Block: 1411038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36635 RingCT/type: yes/0
Extra: 01cbf00c742ea64088d4c5c6323e9eb6065ea3a0970256cd8edb758d37f027b13302110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0706d52f517e1e77dd56926f84e47b1dfd5e4e02bb29a916954f450827943d6 0.600000000000 1899495 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": 1411048, "vin": [ { "gen": { "height": 1411038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0706d52f517e1e77dd56926f84e47b1dfd5e4e02bb29a916954f450827943d6" } } ], "extra": [ 1, 203, 240, 12, 116, 46, 166, 64, 136, 212, 197, 198, 50, 62, 158, 182, 6, 94, 163, 160, 151, 2, 86, 205, 142, 219, 117, 141, 55, 240, 39, 177, 51, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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