Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5e8c0f2bbbdb95cc555af9eafb96af4f817c1d87ce88e70bb848afb5dfa208

Tx prefix hash: 1d1e324cf518c7a4104faf0ef6fd395a8eb551df32d67bdafceb6876c8e21f70
Tx public key: 8ee17c8bfbbfc9022b6179abf6eb77cbf7f9d74be4cd90aa9b1029c48177d249
Timestamp: 1761759617 Timestamp [UCT]: 2025-10-29 17:40:17 Age [y:d:h:m:s]: 00:055:14:53:05
Block: 1400653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39805 RingCT/type: yes/0
Extra: 018ee17c8bfbbfc9022b6179abf6eb77cbf7f9d74be4cd90aa9b1029c48177d24902110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4053679c4ddd51b3498153de375dd5a1c4c62d62a17d3ee3756de2f69f0bae3f 0.600000000000 1888970 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": 1400663, "vin": [ { "gen": { "height": 1400653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4053679c4ddd51b3498153de375dd5a1c4c62d62a17d3ee3756de2f69f0bae3f" } } ], "extra": [ 1, 142, 225, 124, 139, 251, 191, 201, 2, 43, 97, 121, 171, 246, 235, 119, 203, 247, 249, 215, 75, 228, 205, 144, 170, 155, 16, 41, 196, 129, 119, 210, 73, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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