Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bba16a4fd6aa8217c8a293daa155d50fe3de92441aca3677fc299298ca635e97

Tx prefix hash: dab74b82bdbd36c43aafb455ff22aeb912132a39f22c668ee8ecc6163efd0656
Tx public key: 54e8d1ebdc583aa95bb21f2cbd89d97e771d5476dc85315c47ef41817509ee39
Timestamp: 1719684815 Timestamp [UCT]: 2024-06-29 18:13:35 Age [y:d:h:m:s]: 00:306:17:10:18
Block: 1054939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219183 RingCT/type: yes/0
Extra: 0154e8d1ebdc583aa95bb21f2cbd89d97e771d5476dc85315c47ef41817509ee390211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03813f8f6a607094da404da8b92bbde11bafefc9e5936604cc9f1e2d264f3f2d 0.600000000000 1525330 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": 1054949, "vin": [ { "gen": { "height": 1054939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03813f8f6a607094da404da8b92bbde11bafefc9e5936604cc9f1e2d264f3f2d" } } ], "extra": [ 1, 84, 232, 209, 235, 220, 88, 58, 169, 91, 178, 31, 44, 189, 137, 217, 126, 119, 29, 84, 118, 220, 133, 49, 92, 71, 239, 65, 129, 117, 9, 238, 57, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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