Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe3e7e2b53d9903071eed25ad61bf8f31430e8c23cecf4b768dd8987e710efe

Tx prefix hash: 4283bde2e47e9bf76b5ef39c95e51aad45bcbce4bc946ba3e7f454cdeeb81ed2
Tx public key: 05dc8846f4f380672bb6dbaae29ac44d046c9c12a4a3bdccc11fd11ac67b6b0a
Timestamp: 1745226538 Timestamp [UCT]: 2025-04-21 09:08:58 Age [y:d:h:m:s]: 00:263:06:07:03
Block: 1266174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185952 RingCT/type: yes/0
Extra: 0105dc8846f4f380672bb6dbaae29ac44d046c9c12a4a3bdccc11fd11ac67b6b0a0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54119c2c39d165a1329d0a7e8ef86f91995e800709811f95e4089c6b71365bba 0.600000000000 1753391 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": 1266184, "vin": [ { "gen": { "height": 1266174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54119c2c39d165a1329d0a7e8ef86f91995e800709811f95e4089c6b71365bba" } } ], "extra": [ 1, 5, 220, 136, 70, 244, 243, 128, 103, 43, 182, 219, 170, 226, 154, 196, 77, 4, 108, 156, 18, 164, 163, 189, 204, 193, 31, 209, 26, 198, 123, 107, 10, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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