Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1058e99474b5a413e545439629d0cf757a6d567efa315ae0a396554a8810191e

Tx prefix hash: 15a9cd893cff09f8796a8cde07fac5ca4c1a7ffc8e6005b574a2f1c29edc11a8
Tx public key: db73d58e466ec228cc6aa8821d784614a642d145e5996a4b15b4d4bc7368c0cb
Timestamp: 1713591998 Timestamp [UCT]: 2024-04-20 05:46:38 Age [y:d:h:m:s]: 00:348:20:17:56
Block: 1004402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249402 RingCT/type: yes/0
Extra: 01db73d58e466ec228cc6aa8821d784614a642d145e5996a4b15b4d4bc7368c0cb02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d830f91ec1c03832c0d3b0323ca14fcf9842f085bb8234a23de0e4b1917bd04a 0.600000000000 1464970 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": 1004412, "vin": [ { "gen": { "height": 1004402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d830f91ec1c03832c0d3b0323ca14fcf9842f085bb8234a23de0e4b1917bd04a" } } ], "extra": [ 1, 219, 115, 213, 142, 70, 110, 194, 40, 204, 106, 168, 130, 29, 120, 70, 20, 166, 66, 209, 69, 229, 153, 106, 75, 21, 180, 212, 188, 115, 104, 192, 203, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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