Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 174295158e6bbff1711b57e92e4bc8bb25f91cd2b624e3f52188873cbe1d9a11

Tx prefix hash: 552a98eb82c1e67325475bc12c9f0eac68200196b458c955d4a23b9caa41c782
Tx public key: 34376084536930d702c249ae3323b946062a349f8bbd732be8e9f0f7e4e118d3
Timestamp: 1699644981 Timestamp [UCT]: 2023-11-10 19:36:21 Age [y:d:h:m:s]: 01:139:22:21:19
Block: 888806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361192 RingCT/type: yes/0
Extra: 0134376084536930d702c249ae3323b946062a349f8bbd732be8e9f0f7e4e118d3021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.696653400000 dcy

stealth address amount amount idx
00: 2041df19eab71cb12880f2d8d3910b2fd8b0ceb1470893ca1f8d1cea4e3de9e7 0.696653400000 1344765 of 0

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": 888816, "vin": [ { "gen": { "height": 888806 } } ], "vout": [ { "amount": 696653400, "target": { "key": "2041df19eab71cb12880f2d8d3910b2fd8b0ceb1470893ca1f8d1cea4e3de9e7" } } ], "extra": [ 1, 52, 55, 96, 132, 83, 105, 48, 215, 2, 194, 73, 174, 51, 35, 185, 70, 6, 42, 52, 159, 139, 189, 115, 43, 232, 233, 240, 247, 228, 225, 24, 211, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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