Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7c42d9c5c864681143c003ad6bdd7220a0f4e193fe084b0b8ccf3df89ba14a1

Tx prefix hash: 900f0445792dd2d011611a481febe6882ac239f6525e53fc2c825790f304cc78
Tx public key: 3a4d3f1db83c610eeb1dd072e88a04bd6ef968a2593050c2ab29d2a9f4b57907
Timestamp: 1761216289 Timestamp [UCT]: 2025-10-23 10:44:49 Age [y:d:h:m:s]: 00:036:00:15:44
Block: 1396148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25774 RingCT/type: yes/0
Extra: 013a4d3f1db83c610eeb1dd072e88a04bd6ef968a2593050c2ab29d2a9f4b57907021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64f9993f0b4da53193dbc32c1922f8ed5293ec128ee34643a150bb5c8a88dede 0.600000000000 1884433 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": 1396158, "vin": [ { "gen": { "height": 1396148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f9993f0b4da53193dbc32c1922f8ed5293ec128ee34643a150bb5c8a88dede" } } ], "extra": [ 1, 58, 77, 63, 29, 184, 60, 97, 14, 235, 29, 208, 114, 232, 138, 4, 189, 110, 249, 104, 162, 89, 48, 80, 194, 171, 41, 210, 169, 244, 181, 121, 7, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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