Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5b71b8d648da92f1970912378aea64499c9f821a6ba5fe544b1f2463c9ec81

Tx prefix hash: a437eeb341a429fef4a069b39c4442e1a8def337d6465c0bfb2a1672beeb8b67
Tx public key: e7c7372e05a9ccd5e9f174522ec90e95dad8052fa9d77d5a7296472066dfc634
Timestamp: 1745129797 Timestamp [UCT]: 2025-04-20 06:16:37 Age [y:d:h:m:s]: 00:214:02:02:26
Block: 1265372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150742 RingCT/type: yes/0
Extra: 01e7c7372e05a9ccd5e9f174522ec90e95dad8052fa9d77d5a7296472066dfc6340211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48984bda2f3cc2d16da16c3ca3c92ecd631f3452a4d635da8684bf70e19798a1 0.600000000000 1752579 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": 1265382, "vin": [ { "gen": { "height": 1265372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48984bda2f3cc2d16da16c3ca3c92ecd631f3452a4d635da8684bf70e19798a1" } } ], "extra": [ 1, 231, 199, 55, 46, 5, 169, 204, 213, 233, 241, 116, 82, 46, 201, 14, 149, 218, 216, 5, 47, 169, 215, 125, 90, 114, 150, 71, 32, 102, 223, 198, 52, 2, 17, 0, 0, 0, 9, 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