Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4018fa7337bd858f7705330a05bc2bdf41b00fd3c40a48aaaffc1a0312e631d4

Tx prefix hash: 79663565465f0bdc4072d886e34aa5b9b2f1634bbce19e5b638e42bb8bda95c7
Tx public key: c927f5b3981ee80b62b4e576b4338adaff68fbcdc12db12878880640a3234e8c
Timestamp: 1712277513 Timestamp [UCT]: 2024-04-05 00:38:33 Age [y:d:h:m:s]: 01:040:11:09:58
Block: 993517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289916 RingCT/type: yes/0
Extra: 01c927f5b3981ee80b62b4e576b4338adaff68fbcdc12db12878880640a3234e8c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f930667b57e1db759093c1928cbf05c562e29bf76dbf5459892f6cb0d1f412 0.600000000000 1453903 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": 993527, "vin": [ { "gen": { "height": 993517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f930667b57e1db759093c1928cbf05c562e29bf76dbf5459892f6cb0d1f412" } } ], "extra": [ 1, 201, 39, 245, 179, 152, 30, 232, 11, 98, 180, 229, 118, 180, 51, 138, 218, 255, 104, 251, 205, 193, 45, 177, 40, 120, 136, 6, 64, 163, 35, 78, 140, 2, 17, 0, 0, 0, 7, 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