Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee0ec7dfdefd07cacdf8e2cdc543c71d712d4b52262dd3c70b24af02960e9d8a

Tx prefix hash: 55c4a48f1f1d07315d139531df0637b87aba205429af058660d1f1e041619a4d
Tx public key: e41c5b76b4cf435fb6049befe9d9fbb95467ac4ec392fa82a6237c01708af4fb
Timestamp: 1755316876 Timestamp [UCT]: 2025-08-16 04:01:16 Age [y:d:h:m:s]: 00:137:17:26:18
Block: 1347617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98245 RingCT/type: yes/0
Extra: 01e41c5b76b4cf435fb6049befe9d9fbb95467ac4ec392fa82a6237c01708af4fb021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 815484173d80364be71c44ae22bc7d6f4adc87edf82a5ce67eb740a86d90ec72 0.600000000000 1835536 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": 1347627, "vin": [ { "gen": { "height": 1347617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "815484173d80364be71c44ae22bc7d6f4adc87edf82a5ce67eb740a86d90ec72" } } ], "extra": [ 1, 228, 28, 91, 118, 180, 207, 67, 95, 182, 4, 155, 239, 233, 217, 251, 185, 84, 103, 172, 78, 195, 146, 250, 130, 166, 35, 124, 1, 112, 138, 244, 251, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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