Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a45514762567ff1737ba5ce33f9feeaf5b3ae0e978056e3aa5bc69c6569773c

Tx prefix hash: 5b99fa738fd9dadf472f55b233dd0b0c07464e66fb0661da3b827764148b6cfc
Tx public key: 559e2556b507179edf38f0f97ec0f72b4f9768cb541e85a7d1e9135aed9ad175
Timestamp: 1734542110 Timestamp [UCT]: 2024-12-18 17:15:10 Age [y:d:h:m:s]: 00:108:14:46:50
Block: 1178034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77392 RingCT/type: yes/0
Extra: 01559e2556b507179edf38f0f97ec0f72b4f9768cb541e85a7d1e9135aed9ad1750211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23c7cc78dd5234432a6ef9a08f7402cfbaefc7cbd7e2e1647d0f1949b216e944 0.600000000000 1664417 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": 1178044, "vin": [ { "gen": { "height": 1178034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23c7cc78dd5234432a6ef9a08f7402cfbaefc7cbd7e2e1647d0f1949b216e944" } } ], "extra": [ 1, 85, 158, 37, 86, 181, 7, 23, 158, 223, 56, 240, 249, 126, 192, 247, 43, 79, 151, 104, 203, 84, 30, 133, 167, 209, 233, 19, 90, 237, 154, 209, 117, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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