Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c3c92a1337a2ff53f4941a9bbf6a2ca2b4c3c5a437add54fd08e504ae57b14

Tx prefix hash: 4df016d5e31db48c84dc51c1d24bf5431e8c52d50f0dc5a36d43b4ead3dd052a
Tx public key: eae9d401ea77889b82b83e2bbee6730f27045a4cfec6b740bf2ab45e9f15136e
Timestamp: 1752344279 Timestamp [UCT]: 2025-07-12 18:17:59 Age [y:d:h:m:s]: 00:175:21:43:07
Block: 1324065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124516 RingCT/type: yes/0
Extra: 01eae9d401ea77889b82b83e2bbee6730f27045a4cfec6b740bf2ab45e9f15136e02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0382c4fe4fb2b3251c8d8fe7639115f9320462deeec7a39d3a5c4f78a2e87d5 0.600000000000 1811808 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": 1324075, "vin": [ { "gen": { "height": 1324065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0382c4fe4fb2b3251c8d8fe7639115f9320462deeec7a39d3a5c4f78a2e87d5" } } ], "extra": [ 1, 234, 233, 212, 1, 234, 119, 136, 155, 130, 184, 62, 43, 190, 230, 115, 15, 39, 4, 90, 76, 254, 198, 183, 64, 191, 42, 180, 94, 159, 21, 19, 110, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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