Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea7f6da5f4b8c0461365d27cfab7fe871c0729163e47280b0a84eeed1c45a480

Tx prefix hash: 4f7b348139328a2796c52ca23a04951bdc23b39690d67ced3279619973608113
Tx public key: 9d39c41b547ce5c6ba6ccd1bc3a8ec7afa56137b53af45b05ec5ee51bfb3c3e7
Timestamp: 1718481804 Timestamp [UCT]: 2024-06-15 20:03:24 Age [y:d:h:m:s]: 00:144:17:11:34
Block: 1044982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103566 RingCT/type: yes/0
Extra: 019d39c41b547ce5c6ba6ccd1bc3a8ec7afa56137b53af45b05ec5ee51bfb3c3e7021100000001b428b0c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e377244f5a1fbef11cb1e2da829f59517d01140b0ff375b945f1b0e3c349985e 0.600000000000 1514435 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": 1044992, "vin": [ { "gen": { "height": 1044982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e377244f5a1fbef11cb1e2da829f59517d01140b0ff375b945f1b0e3c349985e" } } ], "extra": [ 1, 157, 57, 196, 27, 84, 124, 229, 198, 186, 108, 205, 27, 195, 168, 236, 122, 250, 86, 19, 123, 83, 175, 69, 176, 94, 197, 238, 81, 191, 179, 195, 231, 2, 17, 0, 0, 0, 1, 180, 40, 176, 196, 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