Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea6d4b4ca174b0437cff9c0a9688773893076c3023d3e46f9dec01c1fab807e6

Tx prefix hash: 66246d1f00170dc3d3057be0636c37824664b1f4b1b781ea9a65a4c1f67750bd
Tx public key: 04df597e0133736502ba3903e1bc6d2e6453a4996281a7f295fef42bdb0f7509
Timestamp: 1749612977 Timestamp [UCT]: 2025-06-11 03:36:17 Age [y:d:h:m:s]: 00:151:06:55:25
Block: 1302501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105802 RingCT/type: yes/0
Extra: 0104df597e0133736502ba3903e1bc6d2e6453a4996281a7f295fef42bdb0f750902110000000dbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7434ec7cc1099053ba1a67da77fec6930f565234f744e01ae5c9f58463e44ec6 0.600000000000 1790072 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": 1302511, "vin": [ { "gen": { "height": 1302501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7434ec7cc1099053ba1a67da77fec6930f565234f744e01ae5c9f58463e44ec6" } } ], "extra": [ 1, 4, 223, 89, 126, 1, 51, 115, 101, 2, 186, 57, 3, 225, 188, 109, 46, 100, 83, 164, 153, 98, 129, 167, 242, 149, 254, 244, 43, 219, 15, 117, 9, 2, 17, 0, 0, 0, 13, 191, 81, 178, 162, 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