Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa4a5b95af5aa3f1699510605a0fd7d789a060fb1ba7995cdae36344d7b5cc3e

Tx prefix hash: 2a4f172c64b5da8eebe510d4b5e04da721a85555a2e28e96850f6c3f9be7ab20
Tx public key: 07b2c392a91355439bda858db1e5742448805125ef2bffbce61f889dfd53de06
Timestamp: 1765318698 Timestamp [UCT]: 2025-12-09 22:18:18 Age [y:d:h:m:s]: 00:014:06:18:54
Block: 1430137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10202 RingCT/type: yes/0
Extra: 0107b2c392a91355439bda858db1e5742448805125ef2bffbce61f889dfd53de06021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc7d00f4db30de4a69d2e245c289747043cad7eaa9df4ae3c014c2050e62b1b 0.600000000000 1918880 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": 1430147, "vin": [ { "gen": { "height": 1430137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc7d00f4db30de4a69d2e245c289747043cad7eaa9df4ae3c014c2050e62b1b" } } ], "extra": [ 1, 7, 178, 195, 146, 169, 19, 85, 67, 155, 218, 133, 141, 177, 229, 116, 36, 72, 128, 81, 37, 239, 43, 255, 188, 230, 31, 136, 157, 253, 83, 222, 6, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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