Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed8cf3bf033dc10af00f215ec4a3a6a32b2acca9699710fc43d1aa188d41ca92

Tx prefix hash: bed8d3dfa90e66666aa1c2fa93edc53cb369352f3c039c6aa5cc221841f33a7f
Tx public key: 78aa9864cfab6dc4d54be5acc1d9a39df0869811518aa887a9d1c9ad209b339f
Timestamp: 1672958130 Timestamp [UCT]: 2023-01-05 22:35:30 Age [y:d:h:m:s]: 02:095:12:18:53
Block: 668417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589953 RingCT/type: yes/0
Extra: 0178aa9864cfab6dc4d54be5acc1d9a39df0869811518aa887a9d1c9ad209b339f021100000009272bcc39000000000000000000

1 output(s) for total of 3.743320093000 dcy

stealth address amount amount idx
00: 4c0dacf5ef6a1fd98b9502384ba843f782dcaaf5ae909d178630b76b97c82a5b 3.743320093000 1109664 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": 668427, "vin": [ { "gen": { "height": 668417 } } ], "vout": [ { "amount": 3743320093, "target": { "key": "4c0dacf5ef6a1fd98b9502384ba843f782dcaaf5ae909d178630b76b97c82a5b" } } ], "extra": [ 1, 120, 170, 152, 100, 207, 171, 109, 196, 213, 75, 229, 172, 193, 217, 163, 157, 240, 134, 152, 17, 81, 138, 168, 135, 169, 209, 201, 173, 32, 155, 51, 159, 2, 17, 0, 0, 0, 9, 39, 43, 204, 57, 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