Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb7e9ca1d6f467e26f84ea05c185065abab7a7c4f06cd6c35fb979ed7a120c8f

Tx prefix hash: 29625494c4cd37d8524482ac013be1dbbc820eff0b6ffa711b13b4a88dca5746
Tx public key: c72c34f73d5669f039fee6fbd29b28e3a437fcdc622c3cf8e4a03be169882a76
Timestamp: 1751412770 Timestamp [UCT]: 2025-07-01 23:32:50 Age [y:d:h:m:s]: 00:209:14:13:23
Block: 1316856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147932 RingCT/type: yes/0
Extra: 01c72c34f73d5669f039fee6fbd29b28e3a437fcdc622c3cf8e4a03be169882a7602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5645b19d7038ff2deb393bf043ac78399ee143e27893fd2ddb65f8fc387f4dc 0.600000000000 1804519 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": 1316866, "vin": [ { "gen": { "height": 1316856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5645b19d7038ff2deb393bf043ac78399ee143e27893fd2ddb65f8fc387f4dc" } } ], "extra": [ 1, 199, 44, 52, 247, 61, 86, 105, 240, 57, 254, 230, 251, 210, 155, 40, 227, 164, 55, 252, 220, 98, 44, 60, 248, 228, 160, 59, 225, 105, 136, 42, 118, 2, 17, 0, 0, 0, 1, 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