Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9159e27432f33803a9a2d491f1b5f3fe54539a2018509246f49d9327fb4a35

Tx prefix hash: b8626f178b0cbc24b9a372d03f69fa609b3de6cc70f9684eda826b2c3e22d70d
Tx public key: 5be763cad5e9a60b42c94d6f3b6862880a2d633b58ffda2eccc505e226eaf0b1
Timestamp: 1764564397 Timestamp [UCT]: 2025-12-01 04:46:37 Age [y:d:h:m:s]: 00:022:05:52:30
Block: 1423885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15912 RingCT/type: yes/0
Extra: 015be763cad5e9a60b42c94d6f3b6862880a2d633b58ffda2eccc505e226eaf0b10211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 230123ebe57ca0c94d07c36051d412660078d9a37a88842d69aca49d07c45b7c 0.600000000000 1912512 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": 1423895, "vin": [ { "gen": { "height": 1423885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "230123ebe57ca0c94d07c36051d412660078d9a37a88842d69aca49d07c45b7c" } } ], "extra": [ 1, 91, 231, 99, 202, 213, 233, 166, 11, 66, 201, 77, 111, 59, 104, 98, 136, 10, 45, 99, 59, 88, 255, 218, 46, 204, 197, 5, 226, 38, 234, 240, 177, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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