Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98c7e7b65abbdf67afff7b9badf1647d954ffc5a31df4c40f634aa0f65107b98

Tx prefix hash: be264c2053fc79e306525582b31186c4f5aaad00ad4ab3f9b91304b2d3c9db5e
Tx public key: 2c0415a0142b7b3dfd38d27ae3fea1f40a9aae612b89886f3c1009fc089aaf39
Timestamp: 1696773606 Timestamp [UCT]: 2023-10-08 14:00:06 Age [y:d:h:m:s]: 01:182:10:00:40
Block: 865214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391385 RingCT/type: yes/0
Extra: 012c0415a0142b7b3dfd38d27ae3fea1f40a9aae612b89886f3c1009fc089aaf39021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.834040010000 dcy

stealth address amount amount idx
00: 1c96f300e22d2802d90c77c3275fba4321590652291bbce3293a70e27c13f74c 0.834040010000 1319742 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": 865224, "vin": [ { "gen": { "height": 865214 } } ], "vout": [ { "amount": 834040010, "target": { "key": "1c96f300e22d2802d90c77c3275fba4321590652291bbce3293a70e27c13f74c" } } ], "extra": [ 1, 44, 4, 21, 160, 20, 43, 123, 61, 253, 56, 210, 122, 227, 254, 161, 244, 10, 154, 174, 97, 43, 137, 136, 111, 60, 16, 9, 252, 8, 154, 175, 57, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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