Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1a18e9f101fe5573f948d8e783da9510d14832d3d15cc83a4ed451ce1337d5c

Tx prefix hash: e51606b77e330e183294cdbd1c108149981abfb7344cc1b7fd3853065160a20e
Tx public key: 004a875d3257bc4c247724a414379cfbc3e4f8fa35f542fbd8a09154cd58965a
Timestamp: 1702795522 Timestamp [UCT]: 2023-12-17 06:45:22 Age [y:d:h:m:s]: 01:033:22:09:03
Block: 914923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285557 RingCT/type: yes/0
Extra: 01004a875d3257bc4c247724a414379cfbc3e4f8fa35f542fbd8a09154cd58965a021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a4f0798bec4bb38aea3cbc70aa0df52236f25c97f1525f98d8274e3b5f3b692 0.600000000000 1372279 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": 914933, "vin": [ { "gen": { "height": 914923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a4f0798bec4bb38aea3cbc70aa0df52236f25c97f1525f98d8274e3b5f3b692" } } ], "extra": [ 1, 0, 74, 135, 93, 50, 87, 188, 76, 36, 119, 36, 164, 20, 55, 156, 251, 195, 228, 248, 250, 53, 245, 66, 251, 216, 160, 145, 84, 205, 88, 150, 90, 2, 17, 0, 0, 0, 2, 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