Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85d7c59b0f10c35890a1539723a1fa9407adfa3f8c1a244f6478271805d7ad96

Tx prefix hash: 84d4809ae1320706176c44c40293a4a938b70313c6ed7c3c87d3e93d01b5a4eb
Tx public key: 17ea591352b1912b47af00ad1b7847218578a516bcd3b476ffbbb5338c909a06
Timestamp: 1727033905 Timestamp [UCT]: 2024-09-22 19:38:25 Age [y:d:h:m:s]: 00:108:13:35:49
Block: 1115873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77625 RingCT/type: yes/0
Extra: 0117ea591352b1912b47af00ad1b7847218578a516bcd3b476ffbbb5338c909a0602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3ff4cae7b5d3f8a0250dfa49e744c2180eba4b8b638b82533fd5ad57084071e 0.600000000000 1596154 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": 1115883, "vin": [ { "gen": { "height": 1115873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3ff4cae7b5d3f8a0250dfa49e744c2180eba4b8b638b82533fd5ad57084071e" } } ], "extra": [ 1, 23, 234, 89, 19, 82, 177, 145, 43, 71, 175, 0, 173, 27, 120, 71, 33, 133, 120, 165, 22, 188, 211, 180, 118, 255, 187, 181, 51, 140, 144, 154, 6, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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