Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d05215f03a575f8baa7b83c6160df4174e39032fa1991d504deb3b8e09305331

Tx prefix hash: a202fdd298a15e6fd4f13f60a33e6abbce7f72c6c5805fd8c71be0a0f7ed4eda
Tx public key: f7aa0b0da474e51971d624f661ac437db321ebadefc819eb524b5e8bbfb2c81e
Timestamp: 1718739970 Timestamp [UCT]: 2024-06-18 19:46:10 Age [y:d:h:m:s]: 01:143:07:09:58
Block: 1047107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360965 RingCT/type: yes/0
Extra: 01f7aa0b0da474e51971d624f661ac437db321ebadefc819eb524b5e8bbfb2c81e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72bf242a7bd937df119b14b5db74f011f5d580729a47e01fbadc8f6a34192a26 0.600000000000 1516926 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": 1047117, "vin": [ { "gen": { "height": 1047107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72bf242a7bd937df119b14b5db74f011f5d580729a47e01fbadc8f6a34192a26" } } ], "extra": [ 1, 247, 170, 11, 13, 164, 116, 229, 25, 113, 214, 36, 246, 97, 172, 67, 125, 179, 33, 235, 173, 239, 200, 25, 235, 82, 75, 94, 139, 191, 178, 200, 30, 2, 17, 0, 0, 0, 3, 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