Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966734eddc3e2b6b5af2235e0bfde7dba9063e23e7bb4ffed9af4e393ab1f9dc

Tx prefix hash: 8fda3d9932668b20d1eb335c775b4b88ba06b45653dafd03083ce133bd629673
Tx public key: 030d23c7e0561e7479955ec04a2873fd5be2e89a8447c17531eb4e29e6c2419e
Timestamp: 1617328213 Timestamp [UCT]: 2021-04-02 01:50:13 Age [y:d:h:m:s]: 03:310:18:16:28
Block: 231517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 981340 RingCT/type: yes/0
Extra: 01030d23c7e0561e7479955ec04a2873fd5be2e89a8447c17531eb4e29e6c2419e0211000000153634f08d000000000000000000

1 output(s) for total of 104.934607063000 dcy

stealth address amount amount idx
00: c98ccbd76cbba8fb8bf2d8f9a987558b63cae47959baa4fae7e679f028cf4ad1 104.934607063000 480917 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": 231527, "vin": [ { "gen": { "height": 231517 } } ], "vout": [ { "amount": 104934607063, "target": { "key": "c98ccbd76cbba8fb8bf2d8f9a987558b63cae47959baa4fae7e679f028cf4ad1" } } ], "extra": [ 1, 3, 13, 35, 199, 224, 86, 30, 116, 121, 149, 94, 192, 74, 40, 115, 253, 91, 226, 232, 154, 132, 71, 193, 117, 49, 235, 78, 41, 230, 194, 65, 158, 2, 17, 0, 0, 0, 21, 54, 52, 240, 141, 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