Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b5b6c210c36c3f252db35161a2c75f307fa6177ea278f31c9713cc0a6feddb2

Tx prefix hash: af02f84de20954f97ebca3a8e11213710a96c8e3d7f2f852e4e2a233ab7ef307
Tx public key: 3f851c50b287049a587f79aeb1e8547de8d150fa84857efdd1788acbee570d2e
Timestamp: 1674914303 Timestamp [UCT]: 2023-01-28 13:58:23 Age [y:d:h:m:s]: 02:070:08:37:26
Block: 684654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571900 RingCT/type: yes/0
Extra: 013f851c50b287049a587f79aeb1e8547de8d150fa84857efdd1788acbee570d2e0211000000035029cbac000000000000000000

1 output(s) for total of 3.307173812000 dcy

stealth address amount amount idx
00: 957914b6e8eccb8976024b88f22bae06c5b89bdf2497cfaaf7f4258d6a50d8c8 3.307173812000 1126919 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": 684664, "vin": [ { "gen": { "height": 684654 } } ], "vout": [ { "amount": 3307173812, "target": { "key": "957914b6e8eccb8976024b88f22bae06c5b89bdf2497cfaaf7f4258d6a50d8c8" } } ], "extra": [ 1, 63, 133, 28, 80, 178, 135, 4, 154, 88, 127, 121, 174, 177, 232, 84, 125, 232, 209, 80, 250, 132, 133, 126, 253, 209, 120, 138, 203, 238, 87, 13, 46, 2, 17, 0, 0, 0, 3, 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