Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14b8ef9905fbff1b49a93384f18c39a94df3d630495850ce0436fe77408161be

Tx prefix hash: 2fa9d6175b22e362c004b865e84a68b72da36bd674d0262185bae0f7ec5ea1da
Tx public key: a752f130467a7eb13e2fe1ccc23d86a9e35a9ed639b1fc0bf5bfcb3c62cc092a
Timestamp: 1745464355 Timestamp [UCT]: 2025-04-24 03:12:35 Age [y:d:h:m:s]: 00:211:06:27:23
Block: 1268153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148707 RingCT/type: yes/0
Extra: 01a752f130467a7eb13e2fe1ccc23d86a9e35a9ed639b1fc0bf5bfcb3c62cc092a021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84814340fbb4deafb2eb7f6efa6dc2d164d6e2ae4642809a20eb8a575764fb63 0.600000000000 1755382 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": 1268163, "vin": [ { "gen": { "height": 1268153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84814340fbb4deafb2eb7f6efa6dc2d164d6e2ae4642809a20eb8a575764fb63" } } ], "extra": [ 1, 167, 82, 241, 48, 70, 122, 126, 177, 62, 47, 225, 204, 194, 61, 134, 169, 227, 90, 158, 214, 57, 177, 252, 11, 245, 191, 203, 60, 98, 204, 9, 42, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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