Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9265723051e0ebf3786f849ff267609afb52ba007913eac2af3a322c9b28606e

Tx prefix hash: ee7e760aa1863052a007c93923d073b9bdc41cb90f491208fd2091073d75cabb
Tx public key: ffcc0e8af7131b6d886bfba0ff63b4f23b7f1ce3d30b1210cbe53276fcf0e959
Timestamp: 1755638213 Timestamp [UCT]: 2025-08-19 21:16:53 Age [y:d:h:m:s]: 00:093:01:09:51
Block: 1350120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66410 RingCT/type: yes/0
Extra: 01ffcc0e8af7131b6d886bfba0ff63b4f23b7f1ce3d30b1210cbe53276fcf0e959021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a83c512a1eb25553027ff66fa9f7b7004879f9b3f14b9411303ad8e155cb3446 0.600000000000 1838061 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": 1350130, "vin": [ { "gen": { "height": 1350120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a83c512a1eb25553027ff66fa9f7b7004879f9b3f14b9411303ad8e155cb3446" } } ], "extra": [ 1, 255, 204, 14, 138, 247, 19, 27, 109, 136, 107, 251, 160, 255, 99, 180, 242, 59, 127, 28, 227, 211, 11, 18, 16, 203, 229, 50, 118, 252, 240, 233, 89, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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