Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9f3ca72d703cab2b67681070c2f36f4c4da70bdd55cf634a9e4d19d90ca3a9

Tx prefix hash: 6bfb419ba45f4053f3e881429f950f2942094a55f18aaeab7b00160473035ff0
Tx public key: 7e38050b23a2958b03b6f8f58d91d9d01667fe9d732d97a2195ea56e7cd0da1d
Timestamp: 1682537700 Timestamp [UCT]: 2023-04-26 19:35:00 Age [y:d:h:m:s]: 01:346:00:09:48
Block: 747222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508541 RingCT/type: yes/0
Extra: 017e38050b23a2958b03b6f8f58d91d9d01667fe9d732d97a2195ea56e7cd0da1d021100000002faf35c9c000000000000000000

1 output(s) for total of 2.051840201000 dcy

stealth address amount amount idx
00: 1b19a4e91b4953d2ea072b304be890b38a9cbcd360a481f3d3f2886b549d5357 2.051840201000 1194869 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": 747232, "vin": [ { "gen": { "height": 747222 } } ], "vout": [ { "amount": 2051840201, "target": { "key": "1b19a4e91b4953d2ea072b304be890b38a9cbcd360a481f3d3f2886b549d5357" } } ], "extra": [ 1, 126, 56, 5, 11, 35, 162, 149, 139, 3, 182, 248, 245, 141, 145, 217, 208, 22, 103, 254, 157, 115, 45, 151, 162, 25, 94, 165, 110, 124, 208, 218, 29, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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