Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85afad296007579c4a59de478019bc7c8f6a78b7b87bb6976a5d31ae5012181

Tx prefix hash: 9617db10ba9e529fe3671122b5f2cfe1901e366f758906ea23f89b99db430d0d
Tx public key: 506f775a310dae56a8bf3d5e555d5a2e70021cb3e8e9f813b230847ec94b80b8
Timestamp: 1697560256 Timestamp [UCT]: 2023-10-17 16:30:56 Age [y:d:h:m:s]: 01:001:22:02:56
Block: 871721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262624 RingCT/type: yes/0
Extra: 01506f775a310dae56a8bf3d5e555d5a2e70021cb3e8e9f813b230847ec94b80b8021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.793645363000 dcy

stealth address amount amount idx
00: 522c868b21f5722dfd4e2d66aa0f975f31fa5ff782368e6556b7ec42d15c9a3e 0.793645363000 1326746 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": 871731, "vin": [ { "gen": { "height": 871721 } } ], "vout": [ { "amount": 793645363, "target": { "key": "522c868b21f5722dfd4e2d66aa0f975f31fa5ff782368e6556b7ec42d15c9a3e" } } ], "extra": [ 1, 80, 111, 119, 90, 49, 13, 174, 86, 168, 191, 61, 94, 85, 93, 90, 46, 112, 2, 28, 179, 232, 233, 248, 19, 178, 48, 132, 126, 201, 75, 128, 184, 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