Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a31d922fa2adc2ec6f16240d1542bdb01623c8a0bb25806ee03ee9a89b82643

Tx prefix hash: 8a11e2301c83ec5e77c9124311aa753a99987c49cd1a1901f09a04bbc688515a
Tx public key: fcf732e71397aa0dfc854e3b9eb52f64be0602932bfbff408cf2c92d08c80633
Timestamp: 1708221949 Timestamp [UCT]: 2024-02-18 02:05:49 Age [y:d:h:m:s]: 01:054:08:39:08
Block: 959902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299886 RingCT/type: yes/0
Extra: 01fcf732e71397aa0dfc854e3b9eb52f64be0602932bfbff408cf2c92d08c806330211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eba0f755009c36e1ae2ae6b26620d80271fd78d84b7f4b2fd58e8b4c2aa20eb 0.600000000000 1419461 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": 959912, "vin": [ { "gen": { "height": 959902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eba0f755009c36e1ae2ae6b26620d80271fd78d84b7f4b2fd58e8b4c2aa20eb" } } ], "extra": [ 1, 252, 247, 50, 231, 19, 151, 170, 13, 252, 133, 78, 59, 158, 181, 47, 100, 190, 6, 2, 147, 43, 251, 255, 64, 140, 242, 201, 45, 8, 200, 6, 51, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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