Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e87d9780a4cbb4ab120ed4ec045b74d1e1bb77054f2b3217bfbd69d4a36556a

Tx prefix hash: 2267e2b1ae4f99d95cfafe29734826903f86ee6e5b0693d775b0f98759787352
Tx public key: ee974a1afd0c064d7c2a2ce76face8c21d776641b4e575b06c337dfe439a06f2
Timestamp: 1697846114 Timestamp [UCT]: 2023-10-20 23:55:14 Age [y:d:h:m:s]: 01:129:07:40:15
Block: 874088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353413 RingCT/type: yes/0
Extra: 01ee974a1afd0c064d7c2a2ce76face8c21d776641b4e575b06c337dfe439a06f2021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.779441681000 dcy

stealth address amount amount idx
00: b37fed10aef689cbab17ce094808e5adae66e54e527eea45aaa334d497154d48 0.779441681000 1329284 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": 874098, "vin": [ { "gen": { "height": 874088 } } ], "vout": [ { "amount": 779441681, "target": { "key": "b37fed10aef689cbab17ce094808e5adae66e54e527eea45aaa334d497154d48" } } ], "extra": [ 1, 238, 151, 74, 26, 253, 12, 6, 77, 124, 42, 44, 231, 111, 172, 232, 194, 29, 119, 102, 65, 180, 229, 117, 176, 108, 51, 125, 254, 67, 154, 6, 242, 2, 17, 0, 0, 0, 5, 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