Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a90445f9cd662bb0cf3c702746f650cb3717233cc833ae2145e624a1fb70cd3e

Tx prefix hash: 2d34e82ce75a836fcbd0712224dc36c9b0f201e598aaff4b107cd1ddf2a2e568
Tx public key: e31f2f24ba7ae21c0203862310529d2c192392ccf4e1d3b6dfac571c35c628b1
Timestamp: 1745195721 Timestamp [UCT]: 2025-04-21 00:35:21 Age [y:d:h:m:s]: 00:047:18:47:02
Block: 1265912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34205 RingCT/type: yes/0
Extra: 01e31f2f24ba7ae21c0203862310529d2c192392ccf4e1d3b6dfac571c35c628b1021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e7e09b04db6a4ef4756ef7e64c090e8d1d8787dcc9ac7655226c70b8c0c70b7 0.600000000000 1753125 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": 1265922, "vin": [ { "gen": { "height": 1265912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e7e09b04db6a4ef4756ef7e64c090e8d1d8787dcc9ac7655226c70b8c0c70b7" } } ], "extra": [ 1, 227, 31, 47, 36, 186, 122, 226, 28, 2, 3, 134, 35, 16, 82, 157, 44, 25, 35, 146, 204, 244, 225, 211, 182, 223, 172, 87, 28, 53, 198, 40, 177, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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