Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 225ad93ce6798e4a40aec885dea898d09a3c6cd02d7d4fdbc3461d0aabc9aa43

Tx prefix hash: f23c6f9cbd6b529144cdaf4b1e0f0c9ced2b672f6f06656b60439a64ce37055e
Tx public key: fabfa79504f9d2167a5654315cb2f8d7c60311e37d1c18a2659597019fde899b
Timestamp: 1685328210 Timestamp [UCT]: 2023-05-29 02:43:30 Age [y:d:h:m:s]: 01:312:05:58:52
Block: 770359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484379 RingCT/type: yes/0
Extra: 01fabfa79504f9d2167a5654315cb2f8d7c60311e37d1c18a2659597019fde899b021100000001b3164c24000000000000000000

1 output(s) for total of 1.719812159000 dcy

stealth address amount amount idx
00: e519915756677547a753d888696a4cf97832f99353bb3b2cba7b877cb5e08ac6 1.719812159000 1219664 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": 770369, "vin": [ { "gen": { "height": 770359 } } ], "vout": [ { "amount": 1719812159, "target": { "key": "e519915756677547a753d888696a4cf97832f99353bb3b2cba7b877cb5e08ac6" } } ], "extra": [ 1, 250, 191, 167, 149, 4, 249, 210, 22, 122, 86, 84, 49, 92, 178, 248, 215, 198, 3, 17, 227, 125, 28, 24, 162, 101, 149, 151, 1, 159, 222, 137, 155, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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