Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ed679084ca4972d1a6db195768eb78f9221f764aa31de98325ae2d83539365f

Tx prefix hash: 80f235e664a943e82e592066a15a6be576f03a825f10ee4fa5ed18e1fd60b1f6
Tx public key: 6691e9d4eab12c31c4e547a71af98cf36ae6b061a4c7798c1c37e1ce5374ace3
Timestamp: 1718646990 Timestamp [UCT]: 2024-06-17 17:56:30 Age [y:d:h:m:s]: 00:160:08:42:54
Block: 1046342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114767 RingCT/type: yes/0
Extra: 016691e9d4eab12c31c4e547a71af98cf36ae6b061a4c7798c1c37e1ce5374ace30211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5252040e00029325ab7ec5531ae9aa046a835dcce443b0f848592abee5e76a9 0.600000000000 1516153 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": 1046352, "vin": [ { "gen": { "height": 1046342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5252040e00029325ab7ec5531ae9aa046a835dcce443b0f848592abee5e76a9" } } ], "extra": [ 1, 102, 145, 233, 212, 234, 177, 44, 49, 196, 229, 71, 167, 26, 249, 140, 243, 106, 230, 176, 97, 164, 199, 121, 140, 28, 55, 225, 206, 83, 116, 172, 227, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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