Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3305911dc65494cc58090b5eccc390120c385292f92df33cc992d1e2d2810332

Tx prefix hash: 670fd1fa70616f48618480fb7a36a064463cb357e4d8601e2056e7dcb3de27cf
Tx public key: b660432f75a8884f65c00c089df00318f2619e05cd238fe7642e55a1a09b2839
Timestamp: 1634666965 Timestamp [UCT]: 2021-10-19 18:09:25 Age [y:d:h:m:s]: 03:146:05:07:58
Block: 356330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 882398 RingCT/type: yes/0
Extra: 01b660432f75a8884f65c00c089df00318f2619e05cd238fe7642e55a1a09b28390211000000075410958b000000000000000000

1 output(s) for total of 40.488454988000 dcy

stealth address amount amount idx
00: 1f1d7ab7b813ce4ff071dd74a3b2cb7d182ed65951f74812c5efbd0a4a62eb78 40.488454988000 727080 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": 356340, "vin": [ { "gen": { "height": 356330 } } ], "vout": [ { "amount": 40488454988, "target": { "key": "1f1d7ab7b813ce4ff071dd74a3b2cb7d182ed65951f74812c5efbd0a4a62eb78" } } ], "extra": [ 1, 182, 96, 67, 47, 117, 168, 136, 79, 101, 192, 12, 8, 157, 240, 3, 24, 242, 97, 158, 5, 205, 35, 143, 231, 100, 46, 85, 161, 160, 155, 40, 57, 2, 17, 0, 0, 0, 7, 84, 16, 149, 139, 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