Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e9bbbae4e0861d029cc31792f51b91eaa65d084984523be190fbcd085dbdf26

Tx prefix hash: 1073908bb1458886013b2c4892d901e54db5011af9a6b95041f7701b6e94e3e4
Tx public key: f23fe24e047e4c272c31b832c9a26ec335177cb6926c7f63c7299ca722f24413
Timestamp: 1755076417 Timestamp [UCT]: 2025-08-13 09:13:37 Age [y:d:h:m:s]: 00:098:09:23:17
Block: 1345964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69741 RingCT/type: yes/0
Extra: 01f23fe24e047e4c272c31b832c9a26ec335177cb6926c7f63c7299ca722f2441302110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cce456ab7158ae280dc9f17a9bb6e2088ab43f3e0fc8d5d979c9586cfd7f277 0.600000000000 1833861 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": 1345974, "vin": [ { "gen": { "height": 1345964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cce456ab7158ae280dc9f17a9bb6e2088ab43f3e0fc8d5d979c9586cfd7f277" } } ], "extra": [ 1, 242, 63, 226, 78, 4, 126, 76, 39, 44, 49, 184, 50, 201, 162, 110, 195, 53, 23, 124, 182, 146, 108, 127, 99, 199, 41, 156, 167, 34, 242, 68, 19, 2, 17, 0, 0, 0, 3, 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