Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dc871e4a9bc7c83e40abd46465bce24e975be4be502c6357b0be199d10ad8ff

Tx prefix hash: 326131aab0f3ef057e8d3d6eadeaf983e5ff374d96e25c5fa15a812cff32b028
Tx public key: d41fb72d10c70bc708fd8e214921b0d66d7c0295ef2c1cd7e6ebe6e8c39a14b9
Timestamp: 1675544369 Timestamp [UCT]: 2023-02-04 20:59:29 Age [y:d:h:m:s]: 01:349:15:20:46
Block: 689878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510830 RingCT/type: yes/0
Extra: 01d41fb72d10c70bc708fd8e214921b0d66d7c0295ef2c1cd7e6ebe6e8c39a14b90211000000015029cbac000000000000000000

1 output(s) for total of 3.177954918000 dcy

stealth address amount amount idx
00: abe7fa1abe6525af450a80478422c37a240d4dc77fb1ceb8ad6ddaca15f9b1d3 3.177954918000 1132580 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": 689888, "vin": [ { "gen": { "height": 689878 } } ], "vout": [ { "amount": 3177954918, "target": { "key": "abe7fa1abe6525af450a80478422c37a240d4dc77fb1ceb8ad6ddaca15f9b1d3" } } ], "extra": [ 1, 212, 31, 183, 45, 16, 199, 11, 199, 8, 253, 142, 33, 73, 33, 176, 214, 109, 124, 2, 149, 239, 44, 28, 215, 230, 235, 230, 232, 195, 154, 20, 185, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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